I did some investigation around clangd and the possibility to run it in the browser already, here's what I've found:

• there are some official investigation on how to make it fully support WASI out of the box: Conditionalize use of POSIX features missing on WASI/WebAssembly llvm/llvm-project#92677
• VSCode has an implementation of the WASI protocol in the extension host using https://marketplace.visualstudio.com/items?itemName=ms-vscode.wasm-wasi-core

I was able to run a small C program compiled into wasm, properly accessing the VSCode virtual filesystem. But since it doesn't support some basic features like threads, it failed to run any "advanced" binaries

The only option currently seems to be https://github.com/guyutongxue/clangd-in-browser, but I wonder if it's able to interact with the filesystem, and how?

I did some investigation around clangd and the possibility to run it in the browser already

@CGNonofr Great, thanks for sharing 👍 If this becomes fully working in the browser at one point in time (via whatever tech) it will be awesome.

The only option currently seems to be https://github.com/guyutongxue/clangd-in-browser, but I wonder if it's able to interact with the filesystem, and how?

It brings its own virtual file system. You can read and write files (done here: https://github.com/TypeFox/monaco-languageclient/blob/clangd-example/packages/examples/src/clangd/worker/clangd-server.ts)

It brings its own virtual file system. You can read and write files (done here: https://github.com/TypeFox/monaco-languageclient/blob/clangd-example/packages/examples/src/clangd/worker/clangd-server.ts)

Isn't there any way to provide our own implementation instead? which would access the VSCode filesystem? That would be a shame to have to watch the filesystem to register the files one by one

Isn't there any way to provide our own implementation instead?

The wasm already contains the header files meaning when you have it loaded you can read all the header files as far as I understand it. Something must be adjusted in the build process to change that, I guess. I did not investigate any of this so far.

But now we can start to play with it and try things...

@CGNonofr I will open up a second PR with the wrapper improvements and base this one on it. I need to fix some build problems first.

@CGNonofr maybe we should this merge at some, even if there are improvements required and improve it subsequently (file handling needs polishing and even some parts should be extracted out the examples. I have to make up my mind)

The example should contain a sentence that this is still a prototype and the underlying code is still evolving.

@CGNonofr this is ready for merge on my side. There will be improvements.

@CGNonofr thank you. This is the most complex example to date with many different facets. It could also evolve to a more vscode like editor with explorer view by utilizing the views service. The opened file drop-down is just a simple hack for now.